Semiconductor storage device

ABSTRACT

As a semiconductor storage device that can efficiently perform a refresh operation, provided is a semiconductor storage device comprising a non-volatile semiconductor memory storing data in blocks, the block being a unit of data erasing, and a controlling unit monitoring an error count of data stored in a monitored block selected from the blocks and refreshing data in the monitored block in which the error count is equal to or larger than a threshold value.

TECHNICAL FIELD

The present invention relates to a semiconductor storage device. Inparticular, the present invention relates to a semiconductor storagedevice that includes, for example, an NAND flash memory.

BACKGROUND ART

An NAND flash memory is a non-volatile memory that can retaininformation even when power supply is stopped. The NAND flash memory iswidely popular because it has better per-bit cost than other types ofnon-volatile memory. However, with increasing capacity and higherintegration, influence of aged deterioration in written data andread-disturb have been becoming actualized in the NAND flash memory.There is increased risk of retained data becoming degraded and thestored data not being properly reproduced. The read-disturb refers todata corruption accompanying a reading process.

The aged deterioration is a phenomenon in which a floating gate thataccumulates electric charge gradually loses electric charge with timeprogress, thereby causing data error. The read-disturb is a phenomenonin which an error occurs in stored data, because a minute amount ofelectric charge is accumulated in a floating gate of the memory celladjacent to a memory cell from which data is read out.

Problems regarding the aged deterioration and the read-disturb can besolved by correct data being restored through use of an error correctingcode that corrects data errors having occurred. However, because data inthe NAND flash memory remains erroneous, the correct data cannot berestored when an error exceeding a correction capability of the errorcorrecting code occurs as the aged deterioration and the read-disturbfurther proceed.

Complete destruction of data stored in the NAND flash memory can beprevented and data retaining period can be extended by a refreshoperation in which rewriting data in the NAND flash memory is performedafter stored data is read out and error correction is performed.

As a method of extending the data retaining period for data stored inthe NAND flash memory by a refresh operation as mentioned above, forexample, a method can be considered in which a number of times data isread out from the NAND flash memory and the like is counted. Then arefresh operation is performed when the number of times of readoutreaches a specified number. Alternatively, a method can be considered inwhich a refresh operation is performed when an error count (the numberof errors) increases (refer to, for example, Patent Document 1).

However, in the NAND flush memory, errors are less likely to occur indata in a memory cell in which the number of rewriting is smaller. Theerrors in data do not uniformly increase with an elapse of a certain,fixed amount of time. Similarly, in the NAND flash memory, errors indata do not always increase when data is read out more than a specifiednumber of times. Therefore, when a refresh operation is uniformlyperformed based on the number of times data is read out, rather thanbased on reflection on an actual data corruption state, although datacorruption becomes less likely to occur, the refresh operation isneedlessly performed.

Furthermore, because the NAND flash memory is a device such that thenumber of rewriting is limited, life of the NAND flash memory isshortened by the refresh operation being needlessly performed.

On the other hand, when the refresh operation is performed throughmonitoring of the data corruption state, for example, a memory cellread-out operation itself that is performed to monitor the datacorruption state requires an error correcting process to be performed.As a result, an amount of calculation performed and power consumptionincrease.

[Patent Document 1] Japanese Patent Application Laid-open No.2004-326867

The present invention provides a semiconductor storage device that canefficiently perform a refresh, operation.

DISCLOSURE OF INVENTION

A semiconductor storage device comprising:

a non-volatile semiconductor memory storing data in blocks, the blockbeing a unit of data erasing; and

a controlling unit monitoring an error count of data stored in amonitored block selected from the blocks and refreshing data in themonitored block in which the error count is equal to or larger than athreshold value.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of an overall configuration of a semiconductorstorage device according to a first embodiment of the present invention;

FIG. 2 is a diagram explaining a configuration of a first managementtable in the semiconductor storage device according to the firstembodiment;

FIG. 3 is a flowchart of a monitored block selecting process performedin the semiconductor storage device according to the first embodiment;

FIG. 4 is a flowchart of a monitored block registering process forregistering a monitored block to the first management table in thesemiconductor storage device according to the first embodiment;

FIG. 5 is a flowchart of a registering process for registering a blockto the first management table in the semiconductor storage deviceaccording to the first embodiment;

FIG. 6 is a flowchart of an error count monitoring process performed ona block registered to the first management table in the semiconductorstorage device according to the first embodiment;

FIG. 7 is a flowchart of a deleting process for deleting a block onwhich a refresh operation has been performed from the first managementtable in the semiconductor storage device according to the firstembodiment;

FIG. 8 is a diagram explaining a configuration of a second managementtable in the semiconductor storage device according to the firstembodiment;

FIG. 9 is a flowchart of a monitored block selecting process performedin the semiconductor storage device according to the first embodiment;

FIG. 10 is a diagram explaining a configuration of a third managementtable in the semiconductor storage device according to the firstembodiment;

FIG. 11 is a flowchart of a monitored block selecting process performedin the semiconductor storage device according to the first embodiment;

FIG. 12 is a diagram explaining a configuration of a fourth managementtable in the semiconductor storage device according to the firstembodiment;

FIG. 13 is a flowchart of a monitored block selecting process performedin the semiconductor storage device according to the first embodiment;

FIG. 14 is a diagram explaining a configuration of a fifth managementtable in the semiconductor storage device according to the firstembodiment;

FIG. 15 is a flowchart of a registering process for registering a blockto the first management table in the semiconductor storage deviceaccording to the first embodiment;

FIG. 16 is a diagram explaining a configuration of a sixth managementtable in the semiconductor storage device according to the firstembodiment;

FIG. 17 is a flowchart of a deleting process for deleting a blockexcluded from error count monitoring from a first management table of asemiconductor storage device according to a sixth embodiment;

FIG. 18 is a diagram explaining a configuration of a seventh managementtable in the semiconductor storage device according to the firstembodiment;

FIG. 19 is a flowchart of an error count monitoring process performed ona monitored block registered to a first management table in asemiconductor storage device according to a seventh embodiment;

FIG. 20 is a block diagram of a configuration of an SSD in an example ofthe present invention;

FIG. 21 is a block diagram of a configuration of a drive controllingcircuit in the example;

FIG. 22 is a block diagram of a configuration of a processor in theexample of the present invention;

FIG. 23 is a perspective view of an example of a portable computer onwhich the SSD is mounted in the example;

FIG. 24 is a diagram of an example of a system configuration of theportable computer on which the SSD is mounted in the example of thepresent invention.

BEST MODE(S) FOR CARRYING OUT THE INVENTION

Exemplary embodiments of a semiconductor storage device according to thepresent invention are explained in detail in the following withreference to the drawings. The present invention is not limited to thefollowing embodiments as they are, and constituent elements can bevariously modified and put into practice within the scope of theinvention during an implementation stage.

First Embodiment

FIG. 1 is a block diagram of an overall configuration of a semiconductorstorage device 1 according to a first embodiment. The semiconductorstorage device 1 shown in FIG. 1 is an embodiment of the presentinvention. The present invention is not limited to the configuration.

The semiconductor storage device 1 according to the first embodimentincludes a controlling unit 3 and an NAND flash memory 10. Thecontrolling unit 3 includes a central processing unit (CPU) 4, a randomaccess memory (RAM) 5, a host interface (I/F) 6, a timer 7, an NANDinterface (I/F) 8, and a bus 9. The CPU 4 runs programs. The RAM 5stores therein data, programs, and the like. The host I/F 6 communicateswith a host device 2 connected to the semiconductor storage device 1.The NAND I/F 8 controls data transfer performed between the controllingunit 3 and the NAND flash memory 10. The bus 9 connects the CPU 4, theRAM 5, the host I/F 6, the timer 7, and the NAND I/F 8 in a mannerallowing communication.

The NAND flash memory 10 is configured by arraying a plurality ofblocks. A block is a unit by which data is erased. A block includes aplurality of pages. A page is a unit by which data is written and read.

The semiconductor storage device 1 communicates with the host device 2,via the host I/F 6, thereby performing data transfer between the hostdevice 2 and the semiconductor storage device 1 in response to a requestfrom the host device 2. Interpretation of the request from the hostdevice 2 and control of the semiconductor storage device 1 itself arerealized by the CPU 4 interpreting a program stored in the RAM 5 withinthe controlling unit 3. Data provided by the host device 2 is stored inthe NAND flash memory 10. The controlling unit 3 mediates data transferbetween the host device 2 and the NAND flash memory 10.

The controlling unit 3 within the semiconductor storage device 1communicates with the host device 2, via the host I/F 6, therebyperforming data transfer between the RAM 5 within the controlling unit 3and the host device 2. Data transferred from the host device 2 istemporarily retained in the RAM 5 within the controlling unit 3. At aspecified timing, the data is written to the NAND flash memory 10, viathe NAND I/F 8. When the host device 2 makes a readout request, in thecontrolling unit 3, the data is read from the NAND flash memory 10 inresponse to an instruction from the CPU 4, and the read data is storedin the RAM 5 within the controlling unit 3. The controlling unit 3 thentransfers the data stored in the RAM 5 to the host device 2, via thehost I/F 6.

The NAND I/F 8 used when the data is written to and read from the NANDflash memory 10 includes an error correcting unit 21 and an error countdetecting unit 22. The error correcting unit 21 and the error countdetecting unit 22 serve as an error correcting circuit. The errorcorrecting unit 21 provides a function for correcting an error in dataread out from an arbitrary block within the NAND flash memory 10. Theerror count detecting unit 22 provides a function for detecting an errorcount of errors corrected by the error correcting unit 21. A correctioncapability of an error correcting code attached by the error correctingunit 21 is two bits or more. Here, the present embodiment is describedunder a premise that the correction capability is eight bits. However,the present invention is not limited to this error correctioncapability.

When the data in the RAM 5 is written to the NAND flash memory 10, theerror correcting unit 21 calculates the error correcting code of thedata to be written in, and writes the error correcting code in the NANDflash memory 10 with the data. When the data is read out from the NANDflash memory 10, the error correcting unit 21 uses the data read outfrom the NAND flash memory 10 and the error correcting code stored withthe data in the NAND flash memory 10 to correct an error in the readdata. When the error is corrected, the error count detecting unit 22detects an error count of corrected errors and stores therein thedetected error count. Here, the error count of corrected errors isstored in the error count detecting unit 22. However, a location inwhich the error count of corrected errors is stored is not limitedthereto.

When the error correcting unit 21 corrects the error, the NAND I/F 8generates an interrupt to the CPU 4, thereby giving notification that anerror has occurred in the data stored in the NAND flash memory 10. TheCPU 4 then accesses the error count detecting unit 22 in the NAND I/F 8and obtains the count of corrected errors.

The timer 7, when an arbitrary amount of time is set, then internallymeasures time. The timer 7 generates an interrupt to the CPU 4 when theset amount of time elapses. The CPU 4 is notified of the elapse of theset amount of time by the interrupt from the timer 7.

The NAND flash memory 10 stores therein data provided by the host device2 and error correcting codes calculated from the data by the errorcorrecting unit 21 in combination.

The RAM 5 includes a first management table 31. The first managementtable 31 records therein information on blocks requiring a refreshoperation to be performed in a near future. FIG. 2 is a diagramexplaining a configuration of the first management table 31. The firstmanagement table 31 includes a plurality of entries. A block number inthe NAND flash memory 10 is registered to each entry. The firstmanagement table 31 is accessed by an entry number. A block recorded ineach entry is treated as a block in which an error count of storing datais to be monitored (referred to, hereinafter, as a monitored block).

The RAM 5 also may include a second management table 32, a thirdmanagement table 33, a fourth management table 34, a fifth managementtable 35, a sixth management table 36, and a seventh management table37. The second management table 32 to the seventh management table 37will be described hereafter.

According to the first embodiment, when an error occurs in the data readout from the NAND flash memory 10 in response to the request from thehost device 2, whether to monitor the error count of the block storingtherein the data in which the error has occurred is decided throughprocedures shown in FIG. 3. FIG. 3 is a flowchart of a process forselecting a monitored block according to the first embodiment.

First, when the CPU 4 reads the data from a block in the NAND flashmemory 10, the error correcting section 21 corrects the error in theread data. The error count detecting unit 22 detects the count of errorscorrected and stores therein the detected error count. The CPU 4accesses the error count detecting unit 22, acquires the error count ofthe errors that have occurred in the read data, and checks the errorcount (Step S101). The CPU 4 then checks whether the error count isequal to a first threshold value or more (Step S102). The firstthreshold value is a threshold value of the error count used to select ablock to be monitored. Here, for example, the first threshold value is atwo-bit.

When the error count of errors that have occurred in the data read outfrom the block in the NAND flash memory 10 is equal to the firstthreshold value or more (two bits or more) (Yes at Step S102), it ispossible that the error count of the data will further increase due toinfluence of the aged deterioration and the read-disturb. An errorexceeding the correction capability of the error correcting code mayoccur. Therefore, the CPU 4 selects the block in which the error hasoccurred (the block in which the data read out from the NAND flashmemory 10 is stored) as the monitored block and registers the block tothe first management table 31 (Step S103).

When the error count of the errors that have occurred in the data readout from the NAND flash memory 10 is less than the first threshold value(less than two bits) (No at Step S102), the CPU 4 completes the processwithout registering the block to the first management table 31.

The data stored in the block registered to the first management table 31has a high error count. It is very likely that the error count willfurther increase due to the influence of the aged deterioration and theread-disturb. Therefore, the CPU 4 periodically reads out the data inthe block registered to the first management table 31 from the NANDflash memory 10, checks the error count, and monitors increasingtendency in the error count of the data. The CPU 4 performs a refreshoperation on the block when the error count of errors that have occurredin the data stored in the block exceeds a specified number.

If the error count is detected from only the data read out from the NANDflash memory 10 in response to a read request by the host device 2, theaged deterioration occurring in data stored in a block that is rarelyread out from the NAND flash memory 10 cannot be detected. Therefore, itis preferable that data in all areas of the first management table 31 inthe NAND flash memory 10 is read at an arbitrary timing and the errorcount of the data is checked. The arbitrary timing can be when power isturned on, an interval of once every few months, and the like. As aresult, the increasing tendency in the error count can be monitored forthe data stored in blocks that are rarely read out.

FIG. 4 is a flowchart of a process for checking whether a block newlyselected as the monitored block is already registered to the firstmanagement table 31. First, the CPU 4 checks content registered in anNth entry (N is an entry number in the first management table 31) in thefirst management table 31 (Step S111). The CPU 4 judges whether a blockregistered to the Nth entry is the same as the block newly selected asthe monitored block (Step S112).

When the block registered to the Nth entry is the same as the blocknewly selected as the monitored block (Yes at Step S112), the CPU 4completes the process. When the block registered to the Nth entry is notthe same as the block newly selected as the monitored block (No at StepS112), the CPU 4 checks whether the Nth entry is a last entry (StepS113). When the Nth entry is not the last entry (No at Step S113), theCPU 4 returns to Step S111 and increments the entry number by one. Whenthe Nth entry is the last entry (Yes at Step S113), the CPU 4 completesthe process.

Here, when a block newly selected as the monitored block is notregistered to the first management table 31, this block is registered tothe first management table 31 as shown in a flowchart in FIG. 5. FIG. 5is a flowchart of a process for registering the monitored block to thefirst management table 31.

First, the CPU 4 checks the Nth entry (N is an entry number in the firstmanagement table 31) (Step S121) in the first management table 31 andjudges whether the Nth entry is a blank entry (Step S122). When the Nthentry is a blank entry (Yes at Step S122), the CPU 4 registers themonitored block to the blank entry (Step S126) and completes theprocess.

When the Nth entry is not a blank entry (No at Step S122), the CPU 4checks whether the Nth entry is the last entry (Step S123). When the Nthentry is not the last entry (No at Step S123), the CPU 4 returns to StepS121 and increments the entry number by one. When the Nth entry is thelast entry (Yes at Step S123), the CPU 4 forcibly performs the refreshoperation on a block registered to the first management table 31 andcreates a blank entry in the first management table 31 (Step S124).Since the error count of the data in the refreshed block decreases, theCPU 4 deletes the block from the first management table 31. The CPU 4then registers the new monitored block to the blank entry (Step S125)and completes the process.

Next, a method of monitoring the error count of the data in the blockregistered to the first management table 31 will be described. The CPU 4sets a monitoring interval period in the timer 7 within the controllingunit 3. Whenever the timer 7 generates an interrupt, the error count ismonitored by a method shown in a flowchart in FIG. 6. FIG. 6 is aflowchart of a process for monitoring the error count of the blockregistered to the first management table 31.

First, the CPU 4 checks the Nth entry (N is an entry number in the firstmanagement table 31) in the first management table 31 (Step S131). TheCPU 4 judges whether a block is already registered to the Nth entry(Step S132). When a block is not registered (No at Step S132), the CPU 4checks whether the Nth entry is the last entry (Step S136). When the Nthentry is not the last entry (No at Step S136), the CPU 4 returns to StepS131 and increments the entry number by one. When the Nth entry is thelast entry (Yes at Step S136), the CPU 4 completes the process.

At Step S132, when a block is already registered (Yes at Step S132), theCPU 4 reads out the data in the block registered to the Nth entry fromthe NAND flash memory 10 to the RAM 5 within the controlling unit 3.Next, the error correcting unit 21 corrects an error in the read data.The error count detecting unit 22 detects the count of corrected errorsand stores therein the detected error count. The CPU 4 accesses theerror count detecting unit 22, obtains the error count of the errorsthat have occurred in the read data, and checks the error count (StepS133). The CPU 4 then judges whether the error count of the read data isequal to a second threshold value or more (Step S134). The secondthreshold value is a threshold value of the error count used to select ablock in which data is to be rewritten (refreshed) by a predeterminedmethod. Here, for example, the second threshold value is a four-bit. Thesecond threshold value is set taking into consideration the correctioncapability of the error correcting code.

When the error count is less than the second threshold value (less thanfour bits) (No at Step S134), the CPU 4 checks whether the Nth entry isthe last entry (Step S136). When the Nth entry is not the last entry (Noat Step 136), the CPU 4 returns to Step S131 and increments the entrynumber by one. When the Nth entry is the last entry (Yes at Step S136),the CPU 4 completes the process.

At Step S134, when the error count is equal to the second thresholdvalue or more (four bits or more) (Yes at Step S139), the CPU 4 performsa refresh operation on the block registered to the Nth entry (StepS135). The CPU 4 then checks whether the Nth entry is the last entry(Step S136). When the Nth entry is not the last entry (No at Step S136),the CPU 4 returns to Step S131 and increments the entry number by one.When the Nth entry is the last entry (Yes at Step S131), the CPU 4completes the process.

According to the first embodiment, an error count threshold value(second threshold value) for refreshing the monitored block registeredin the first management table 31 is set to be greater than an errorcount threshold value (first threshold value) for registering a block asthe monitored block to the first management table 31. This settingallows a block with a low error count to be monitored, and a block witha high error count to be refreshed because there is a possibility thatdata in a block with a high error count cannot be restored.

To perform the refresh operation on the block, first, all data in theblock to be refreshed are read out from the NAND flash memory 10 to theRAM 5 within the controlling unit 3. The block in the NAND flash memory10 is erased. Then, after the block is erased, all data migrated to theRAM 5 are rewritten in the deleted block. The error count of the data inthe refreshed block decrease. Therefore, the block is deleted from thefirst management table 31 by a method shown in FIG. 7, and is excludedfrom monitored blocks. FIG. 7 is a flowchart of a process for deletingthe refreshed block from the first management table 31.

First, the CPU 4 checks the Nth (N is an entry number in the firstmanagement table 31) entry in the first management table 31 (Step S141).The CPU 4 judges whether the registered block is a subject block, namelya refreshed block (Step S142). When the block is not the subject block(No at Step S142), the CPU 4 checks whether the entry is the last entry(Step S144). When the entry is not the last entry (No at Step S144), theCPU 4 returns to Step S141 and increments the entry number by one. Whenthe entry is the last entry (Yes at Step S144), the CPU 4 completes theprocess.

At Step S142, when the registered block is the subject block (Yes atStep S142), the CPU 4 deletes the block registered in the Nth entry fromthe first management table 31 (Step S143) and completes the process. Thedata can be rewritten in another empty block rather than being rewrittenin the block in which the data had originally been written.

As described above, in the semiconductor storage device 1 according tothe first embodiment, the block in the NAND flash memory 10 storing thedata that will require the refresh operation to be performed in the nearfuture, due to the influence of the aged deterioration and theread-disturb, is selected based on the error count of errors occurringin the data stored in the block. The selected block is registered in thefirst management table 31 as the monitored block of which the errorcount of the data is monitored. Then, the data in the block registeredto the first management table 31 is periodically read and the errorcount is checked. When the error count of the data exceeds a specifiednumber, the refresh operation is performed: In this way, an interval atwhich the refresh operation is performed on the block can be extendedwithin a range of the correction capability of the error correctingcode, thereby reducing the number of refresh operation performed. Thenumber of times the NAND flash memory 10 is rewritten can be controlled.As a result, data corruption caused by the aged deterioration and theread-disturb can be prevented with more certainty by the refreshoperation being less frequently performed. Moreover, a semiconductorstorage device can be actualized in which an amount of processing andpower consumption during the refresh operation is suppressed.

In the semiconductor storage device 1 according to the first embodiment,the error count threshold value (second threshold value) for refreshingthe monitored block registered to the first management table 31 isgreater than the error count threshold value (first threshold value) forregistering a block as the monitored block to the first management table31. As a result, blocks among the monitored blocks having a high errorcount can be refreshed, thereby preventing an instance in which datacannot be restored.

Second Embodiment

According to a second embodiment, a case that a monitored block isselected based on a read-out amount of data stored in a block in theNAND flash memory 10 in the semiconductor storage device 1 of FIG. 1 isdescribed. A method of registering the monitored block according to thesecond embodiment differs from that according to the first embodiment.Other aspects according to the second embodiment are the same as thoseaccording to the first embodiment.

FIG. 8 is a diagram explaining a configuration of a second managementtable 32. The second management table 32 is a management table storingtherein a read-out amount of data in a block in the NAND flash memory10. The second management table 32 is configured in the RAM 5. Thesecond management table 32 stores each of the block numbers in the NANDflash memory 10 and read-out amounts of data read from the blocks.

Whenever the CPU 4 reads out data from a block in the NAND flash memory10, the CPU 4 counts a read-out amount of the data by a number of pages.The CPU 4 stores a page count in the second management table 32 andupdates the page count. The read-out amount stored in the secondmanagement table 32 is a read-out amount counted after the data isstored in the block in the NAND flash memory 10. A value of the read-outamount is cleared whenever the data in the block is erased. Anintegrated quantity of data volume or a read-out frequency can be usedas the read-out amount of the data.

According to the second embodiment, when a read-out process for readingout data from the NAND flash memory 10 in response to a request from thehost device 2 is performed, whether to monitor a block in which an errorhas occurred is decided through procedures shown in FIG. 9. FIG. 9 is aflowchart of a monitored block selecting process according to the secondembodiment.

First, when the read-out process for reading the data from a block inthe NAND flash memory 10 in response to a request from the host device 2is performed, the CPU 4 updates a read-out amount in the secondmanagement table 32 of the data in the block (Step S151). The CPU 4 thenchecks whether the updated read-out amount of the data is equal to athird threshold value or more (Step S152). The third threshold value isa threshold value of the read-out amount of the data from the block usedto select a block to be monitored. Here, for example, the thirdthreshold value is a read-out amount of 10̂10 pages.

When the read-out amount of the data from the block is equal to thethird threshold value or more (Yes at Step S152), it is possible that anerror count will further increase due to the influence of the ageddeterioration and the read-disturb. An error exceeding a correctioncapability of an error correcting code may occur. Therefore, the CPU 4registers the block from which the data is read out to the firstmanagement table 31 as the monitored block (Step S153). When theread-out amount of the data from the block is less than the thirdthreshold value (No at Step S152), the CPU 4 completes the processwithout registering the block to the first management table 31. A methodof monitoring the error count of the data in the blocks registered tothe first management table 31 is similar to that according to the firstembodiment. Detailed descriptions thereof are omitted.

As described above, in the semiconductor storage device 1 according tothe second embodiment, the block in the NAND flash memory 10 storing thedata that will require a refresh operation to be performed in the nearfuture, due to the influence of the aged deterioration and theread-disturb, is selected based on the read-out amount of the datastored in the block. The selected block is registered in the firstmanagement table 31 as the monitored block of which the error count ofthe data is monitored. Then, the data in the block registered to thefirst management table 31 is periodically read and the error count ischecked. When the error count of the data exceeds a specified number,the refresh operation is performed. In this way, an interval at whichthe refresh operation is performed on the block can be extended within arange of the correction capability of the error correcting code, therebyreducing a number of refresh operation performed. The number of timesthe NAND flash memory 10 is rewritten can be controlled. As a result,data corruption due to the aged deterioration and the read-disturb canbe prevented with more certainty by the refresh operation being lessfrequently performed. Moreover, a semiconductor storage device can beactualized in which an amount of processing and power consumption duringthe refresh operation is suppressed.

Third Embodiment

According to a third embodiment, a case that a monitored block isselected based on a writing time at which data is written in a block inthe NAND flash memory 10 in the semiconductor storage device 1 of FIG. 1is described. A method of registering the monitored block according tothe third embodiment differs from that according to the firstembodiment. Other aspects according to the third embodiment are the sameas those according to the first embodiment.

FIG. 10 is a diagram explaining a configuration of a third managementtable 33. The third management table 33 is a management table storingtherein a writing time at which data is written in a block in the NANDflash memory 10. The third management table 33 is configured in the RAM5. The third management table 33 stores each of the block numbers in theNAND flash memory 10 and writing times at which data are written in theblocks.

When the CPU 4 writes data in the block in the NAND flash memory 10, theCPU 4 stores a writing time in the third management table 33. A value ofthe writing time stored in the third management table 33 is clearedwhenever the data in the block in the NAND flash memory is erased. Thewriting time stored in the third management table 33 is merely requiredto indicate a time difference between a point in time at which the datais written and a current time, through use of a total number of erasuresin the NAND flash memory and the like, in addition to an operating timeof the semiconductor storage device 1.

According to the third embodiment, when a read-out process for readingdata from the NAND flash memory 10 in response to a request from thehost device 2 is performed, an amount of elapsed time from when the datais written in the block is measured through procedures shown in FIG. 11.A block of which the error count is to be monitored is decided. FIG. 11is a flowchart of a monitored block selecting process according to thethird embodiment.

First, when the read-out process for reading the data from the NANDflash memory 10 in response to the request from the host device 2 isperformed, the CPU 4 calculates a difference between a writing timestored in the third management table 33 at which a last writingoperation has been performed on the block from which the data is to beread, and a current time. In other words, the CPU 4 calculates an amountof elapsed time from the writing time of the block from which the datais to be read (Step S161). The CPU 4 then checks whether the elapsedtime from the writing time of the block is equal to a fourth thresholdvalue or more (Step S162). The fourth threshold value is a thresholdvalue of an amount of time elapsed from a writing time of the block usedto select the block to be monitored. Here, for example, the fourththreshold value is one month.

When the elapsed time from the writing time of the block is equal to thefourth threshold value or more (Yes at Step S162), it is possible thatan error count will further increase due to the influence of the ageddeterioration and the read-disturb. An error exceeding a correctioncapability of an error correcting code may occur. Therefore, the CPU 4registers the block from which the data is read to the first managementtable 31 as the monitored block (Step S163). When the elapsed time fromthe writing time of the block is less than the fourth threshold value(No at Step S162), the CPU 4 completes the process without registeringthe block to the first management table 31. A method of monitoring theerror count of the data in the blocks registered to the first managementtable 31 is similar to that according to the first embodiment. Detaileddescriptions thereof are omitted.

If the elapsed time from the writing time of the block is checked onlyfor the data read out from the NAND flash memory 10 in response to aread request by the host device 2, the aged deterioration occurring indata stored in a block that is rarely read out from the NAND flashmemory 10 cannot be detected. Therefore, it is preferable that data inall areas of the first management table 31 in the NAND flash memory 10is read at an arbitrary timing and the elapsed time from the writingtime of the blocks is checked. The arbitrary timing can be when power isturned ON, an interval of once every few months, and the like. As aresult, the increasing tendency in the error count can be monitored forthe data stored in blocks that are rarely read.

As described above, in the semiconductor storage device 1 according tothe third embodiment, the block in the NAND flash memory 10 storing thedata that will require a refresh operation to be performed in the nearfuture, due to the influence of the aged deterioration and theread-disturb, is selected based on the elapsed time from a last writingtime of the block. The selected block is registered in the firstmanagement table 31 as the monitored block of which the error count ofthe data is monitored. Then, the data in the block registered to thefirst management table 31 is periodically read and the error count ischecked. When the error count of the data exceeds a specified number,the refresh operation is performed. In this way, an interval at whichthe refresh operation is performed on the block can be extended within arange of the correction capability of the error correcting code, therebyreducing a number of refresh operation performed. A number of times theNAND flash memory 10 is rewritten can be controlled. As a result, datacorruption due to the aged deterioration and the read-disturb can beprevented with more certainty by the refresh operation being lessfrequently performed. Moreover, a semiconductor storage device can beactualized in which an amount of processing and power consumption duringthe refresh operation is suppressed.

Fourth Embodiment

According to a fourth embodiment, a case that a monitored block isselected based on a sequence in which data is written in blocks in theNAND flash memory 10 in the semiconductor storage device 1 of FIG. 1 isdescribed. A method of registering the monitored block according to thefourth embodiment differs from that according to the first embodiment.Other aspects according to the fourth embodiment are the same as thoseaccording to the first embodiment.

FIG. 12 is a diagram explaining a configuration of a fourth managementtable 34. The fourth management table 34 is a management table storingtherein a sequence in which data is written in the blocks in the NANDflash memory 10. The fourth management table 34 is configured in the RAM5. The fourth management table 34 stores each of the block numbers inthe NAND flash memory 10 and corresponding sequence numbers in whichdata is written in the NAND flash memory 10.

When the CPU 4 writes data in a block in the NAND flash memory 10, theCPU 4 stores the sequence number in which the data is written in theNAND flash memory 10 in the fourth management table 34 and updates thefourth management table 34. The fourth management table 34 is preferablyactualized by a linked structure or the like, such that processes to beperformed do not increase even when writing sequence numbers are updatedwhenever a writing process is performed. As a result, processing loadplaced on the CPU 4 can be reduced and processing time can be shortened.

According to the fourth embodiment, when a writing process for writingdata in the NAND flash memory 10 in response to a request from the hostdevice 2 is performed, a sequence number in which data is written in theblocks in the NAND flash memory 10 is stored and the sequence numbersare updated through procedures shown in FIG. 13. A block of which theerror count is to be monitored is decided based on the writing sequencenumber. FIG. 13 is a flowchart of a monitored block selecting processaccording to the fourth embodiment.

First, when the writing process for writing the data in the block in theNAND flash memory 10 in response to the request from the host device 2is performed, the CPU 4 stores the writing sequence number in the fourthmanagement table 34 and updates the writing sequence numbers (StepS171). The CPU 4 then checks a block corresponding to an Nth writingsequence number (N is a writing sequence number in the fourth managementtable 34) in the fourth management table 34 (Step S172). The CPU 4checks whether the writing sequence number is equal to a fifth thresholdvalue or less or, in other words, whether the block is older than thefifth threshold value (Step S173). The fifth threshold value is athreshold value of a writing sequence used to select the block to bemonitored. Here, for example, the fifth threshold value is ten blocksfrom a block with an oldest (smallest) writing sequence number.

When the writing sequence number is equal to the fifth threshold valueor less or, in other words, the block is older than the fifth thresholdvalue (Yes at Step S173), it is possible that an error count willfurther increase due to the influence of the aged deterioration and theread-disturb. An error exceeding a correction capability of an errorcorrecting code may occur. Therefore, the CPU 4 checks whether the blockis registered to the first management table 31 (Step S174). When theblock is not registered to the first management table 31 (No at StepS174), the CPU registers the block to the first management table 31 asthe monitored block (Step S175). In other words, the CPU registers theblock that has been written further in the past than the fifth thresholdvalue in the first management table 31 as the monitored block, andchecks the error count of the data.

At Step S174, when the block is already registered to the firstmanagement table 31 (Yes at Step S174), the CPU 4 checks whether the Nthwriting sequence number is a last writing sequence number (Step S176).When the Nth writing sequence number is not the last writing sequencenumber (No at Step S176), the CPU 4 returns to Step S172 and incrementsthe writing sequence number by one. When the Nth writing sequence numberis the last writing sequence number (Yes at Step S176), the CPU 4completes the process.

At Step S173, when the writing sequence number is not equal to the fifththreshold value or less or, in other words, is a newer block than thefifth threshold value (No at Step S173), the CPU 4 checks whether theNth writing sequence number is the last writing sequence number (StepS176). When the Nth writing sequence number is not the last writingsequence number (No at Step S176), the CPU 4 returns to Step S172 andincrements the writing sequence number by one. When the Nth writingsequence number is the last writing sequence number (Yes at Step S176),the CPU 4 completes the process. A method of monitoring the error countof the data in the blocks registered to the first management table 31 issimilar to that according to the first embodiment. Detailed descriptionsthereof are omitted.

As described above, in the semiconductor storage device 1 according tothe fourth embodiment, the block in the NAND flash memory 10 storing thedata that will require a refresh operation to be performed in the nearfuture, due to the influence of the aged deterioration and theread-disturb, is selected based on the sequence in which the data arewritten in the blocks in the NAND flash memory 10. The selected block isregistered in the first management table 31 as the monitored block ofwhich the error count in the data is monitored. Then, the data in theblock registered to the first management table 31 is periodically readand the error count is checked. When the error count of the data exceedsa specified number, the refresh operation is performed. In this way, aninterval at which the refresh operation is performed on the block can beextended within a range of the correction capability of the errorcorrecting code, thereby reducing a number of refresh operationsperformed. The number of times the NAND flash memory 10 is rewritten canbe controlled. As a result, data corruption due to the ageddeterioration and the read-disturb can be prevented with more certaintyby the refresh operation being less frequently performed. Moreover, asemiconductor storage device can be actualized in which an amount ofprocessing and power consumption during the refresh operation issuppressed.

Fifth Embodiment

According to a fifth embodiment, a process performed when a blank entryis not available when a block is registered to the first managementtable 31 in the semiconductor storage device 1 according to the firstembodiment to the fourth embodiment is described.

FIG. 14 is a diagram explaining a configuration of a fifth managementtable 35. The fifth management table 35 is a management table storingtherein a registration sequence of monitored blocks registered to thefirst management table 31. The fifth management table 35 is configuredin the RAM 5. The fifth management table 35 stores numbers of monitoredblocks registered to the first management table 31 and sequence numbersof a sequence in which the monitored blocks are registered to the firstmanagement table 31 (registration sequence number).

When the monitored blocks are registered to the first management table31, the monitored blocks are sequentially stored such that a monitoredblock that is registered earlier has a lower entry number in the firstmanagement table 31. According to the fifth embodiment, whenever the CPU4 registers a monitored block to the first management table 31, the CPU4 registers a block number of the monitored block to the fifthmanagement table 35. The fifth management table 35 is preferablyactualized by a linked list because the CPU 4 updates the registrationsequence numbers whenever a monitored block is registered to or deletedfrom the first management table 31. As a result, processing load placedon the CPU 4 can be reduced and processing time can be shortened.

A registering process for registering a monitored block to the firstmanagement table 31 performed when a blank entry is not available whenthe monitored block is registered to the first management table 31 willbe described hereafter with reference to FIG. 15. FIG. 15 is a flowchartof a registering process for registering the monitored block to thefirst management table 31 according to the fifth embodiment.

First, when the registering process for registering the monitored blockto the first management table 31 is performed, the CPU 4 checks whethera registered block count of blocks registered to the fifth managementtable 35 is less than a sixth threshold value (Step S181). Here, thesixth threshold value is a maximum number of blocks that can beregistered to the first management table 31 and a maximum number ofblocks that can be registered to the fifth management table 35.Therefore, the registered block count of the blocks registered to thefifth management table 35 being less than the sixth threshold valueindicates that a blank entry is available in the first management table31. The registered block count of the blocks registered to the fifthmanagement table 35 not being less than the sixth threshold valueindicates than a blank entry is not available in the first managementtable 31.

When the registered block count of the blocks registered to the fifthmanagement table 35 is less than the sixth threshold value or, in otherwords, a blank entry is available in the first management table 31 (Yesat Step S181), the CPU 4 registers the monitored block to the blankentry in the first management table 31 (Step S184). The CPU 4 furtherregisters the block number of the monitored block to the fifthmanagement table 35 and completes the process.

When the registered block count of the blocks registered to the fifthmanagement table 35 is less than the sixth threshold value (when a blankentry is not available in the first management table 31) (No at StepS181), the CPU 4 references the fifth management table 5 and refreshesdata in the monitored block of which the registration sequence number inthe fifth management table 35 is earliest (Step S182). In other words,the CPU 4 refreshes data in the block that has been registered to thefirst management table 31 and the fifth management table 35 earliest.

The CPU 4 then deletes the refreshed block from the first managementtable 31 and the fifth management table 35 (Step S183). Subsequently,the CPU 4 registers the new monitored block to the blank entry in thefirst management table 31. The CPU 4 then registers the monitored blockregistered to the blank entry in the first management table 31 to thefifth management table 35 (Step S184).

As described above, in the semiconductor storage device 1 according tothe fifth embodiment, as a result of blank entries in the firstmanagement table 31 being managed, a new monitored block can beregistered to the first management table 31 even when a blank entry isnot available when the monitored block is registered to the firstmanagement table 31. The monitored blocks storing data of which theerror count is monitored can be managed.

Sixth Embodiment

According to a sixth embodiment, a process performed when a block thathas become excluded from data error count monitoring is deleted from thefirst management table 31 in the semiconductor storage device 1according to the first embodiment to the fifth embodiment is described.

FIG. 16 is a diagram explaining a configuration of a sixth managementtable 36. The sixth management table 36 is a management table storingtherein blocks in the NAND flash memory 10 in which data to be retainedis not stored. The sixth management table 36 is configured in the RAM 5.In the sixth management table 36, a block number of a block that doesnot store therein data to be retained, among block numbers of blocks inthe NAND flash memory 10, is registered in each entry. The sixthmanagement table 36 is accessed by entry numbers.

The CPU 4 acquires information from the sixth management table 36 on ablock that does not store therein data to be retained and, as a result,can write a new data in the block. The CPU 4 also registers the block inwhich the data to be retained is no longer present to the sixthmanagement table 36. A state in which the data to be retained is nolonger present occurs mainly when a new data is written. For example,when data X of an address A is stored in a block 1 in the NAND flashmemory 10, in a control method in which control is performed to writedata Y of the address A to another block (such as a block 100) when thehost device 2 requests that the data X of the address A is rewritten tothe data Y, the previous data X of the address A stored in the block 1is no longer data to be retained (invalid data).

A process performed when the monitored block that has become excludedfrom data error count monitoring is deleted from the first managementtable 31 will be described hereafter with reference to FIG. 17. FIG. 17is a flowchart of a deleting process for deleting a block excluded fromerror count monitoring from the first management table according to thesixth embodiment.

First, when a block is generated in which data to be retained is nolonger present, the CPU 4 checks an Nth entry (N is an entry number inthe first management table 31) in the first management table 31 (StepS191). The CPU 4 judges whether a block registered to the Nth entry is asubject block (a block excluded from monitoring in which the data to beretained is no longer present) (Step S192). When the block is not thesubject block (No at Step S192), the CPU 4 judges whether the entry is alast entry (Step S193).

Here, when the entry is not the last entry (No at Step S193), the CPU 4returns to Step S191 and increments the entry number by one. When theentry is the last entry (Yes at Step S193), the CPU 4 completes theprocess.

At Step S192, when the block is the subject block (Yes at Step S192),the CPU 4 performs a deleting process to delete the block from the firstmanagement table 31. The CPU 4 registers the block number of the blockto the sixth management table 36 and completes the process (Step S194).The block registered to the sixth management table 36 is not required tobe updated because the block does not store therein data to be retained.

As described above, in the semiconductor storage device 1 according tothe sixth embodiment, when a block is generated that is excluded frommonitoring and in which data to be retained is no longer present when,for example, new data is written in the block in the NAND flash memoryin which the data is stored, the block that is excluded from monitoringcan be deleted from the first management table 31 with certainty, andblank entries in the first management table 31 can be managed.

Seventh Embodiment

According to a seventh embodiment, a method of monitoring a monitoredblock registered to the first management table 31 in the semiconductorstorage device 1 according to the first embodiment to the sixthembodiment is described.

FIG. 18 is a diagram explaining a configuration of a seventh managementtable 37. The seventh management table 37 is a management table storingtherein error counts of blocks in the NAND flash memory 10 registered tothe first management table 31. The seventh management table 37 isconfigured in the RAM 5. The seventh management table 37 includes aplurality of entries. A block number of a block registered to the firstmanagement table 31 and an error count detected from data stored in theblock are registered to each entry. The seventh management table 37 isaccessed by an entry number. Values of the error counts registered tothe seventh management table 37 are updated whenever error countmonitoring is performed.

The method of monitoring the error count of a monitored block registeredto the first management table 31 will be described hereafter withreference to FIG. 19. FIG. 19 is a flowchart of an error countmonitoring process performed on the monitored block registered to thefirst management table 31.

The CPU 4 sets a monitoring interval period in the timer 7 within thecontrolling unit 3. The error count monitoring process on the monitoredblock registered to the first management table 31 is performed wheneveran interrupt is generated by the timer 7. The timer 7 internallymeasures time when the CPU sets the monitoring interval period. Afterthe set period elapses, the timer 7 generates an interrupt to the CPU 4.

When the timer 7 generates the interrupt, the CPU 4 checks an Nth entry(N is an entry number in the seventh management table 37) of the seventhmanagement table 37 (Step S201). The CPU 4 judges whether a block isalready registered to the Nth entry (Step S202). When a block is notregistered (No at Step S202), the CPU 4 judges whether the Nth entry isa last entry (Step S206). When the Nth entry is not the last entry (Noat Step S206), the CPU 4 returns to Step S201 and increments the entrynumber by one. When the Nth entry is the last entry (Yes at Step S206),the CPU 4 completes the error count monitoring process.

At Step S202, when a block is already registered (Yes at Step S202), theCPU 4 checks an error count (number of bits) of the block registered tothe seventh management table 37 (Step S203). The CPU 4 judges whetherthe error count is equal to a seventh threshold value or more (StepS209). The seventh threshold value is used to select a block on which anerror count detecting process is to be performed, among the monitoredblocks. Here, the seventh threshold value is, for example, four bits oferror.

When the error count is less than the seventh threshold value (less thanfour bits) (No at Step S204), the CPU 4 checks whether the Nth entry isthe last entry (Step S206). When the Nth entry is not the last entry (Noat Step S206), the CPU 4 returns to Step S201 and increments the entrynumber by one. When the Nth entry is the last entry (Yes at Step S206),the CPU 4 completes the error count monitoring process.

At Step S204, when the error count is the seventh threshold value ormore (four bits or more) (Yes at Step S204), the CPU 4 reads out thedata in the block from the NAND flash memory 10 to the RAM 5 within thecontrolling unit 3 and performs an error count detecting process on thedata (Step S205). The CPU 4 updates the seventh management table 37 witha detected error count. Based on the detected error count, the CPU 4performs the refresh operation according to the first embodiment,described with reference to FIG. 6.

Next, the CPU 4 checks whether the Nth entry is the last entry (StepS206). When the Nth entry is not the last entry (No at Step S206), theCPU 4 returns to Step S201 and increments the entry number by one. Whenthe Nth entry is the last entry (Yes at Step S206), the CPU 4 completesthe error count monitoring process.

A value set as the above-described seventh threshold value decreaseswhenever the error count detecting process is performed, graduallyfacilitating error count detection to be performed on blocks with a lowerror count. As a result, the error count detection is performed eachtime on the blocks with a high error count over a short cycle. The errorcount detection is performed on the blocks with a low error count over along cycle. The value set as the seventh threshold value returns to anoriginal value after the value is decreased to a predetermined,specified value.

As described above, in the semiconductor storage device 1 according tothe seventh embodiment, whether an error count detecting process isnewly performed on a monitored block is judged for the monitored blocksregistered to the first management table 31 based on the error countsregistered to the seventh management table 37. The error count detectionis performed on the blocks with a high error count over a short cycle.The error count detection is performed on the blocks with a low errorcount over a long cycle. As a result, the monitoring intervals of themonitored blocks registered to the first management table 31 can bechanged based on the error counts registered to the seventh managementtable 37. The error count of the data in a block that will most likelyrequire updating in the near future, among the monitored blocksregistered to the first management table 31, can be monitored withcertainty. At the same time, frequency of the error count monitoring canbe reduced. As a result, an amount of calculations required to performthe error count monitoring and power consumption can be suppressed.

Eighth Embodiment

According to an eighth embodiment, an error count monitoring cycleaccording to the seventh embodiment will be described. According to theeighth embodiment, regarding a monitoring process performed on monitoredblocks registered to the first management table 31, an upper limit isset for a monitoring cycle (monitoring interval period set in the timer7) of blocks having a low error count.

Here, the upper limit of the monitoring cycle is set to be shorter thanan amount of time required from when an error count of data stored in ablock exceeds the first threshold value until the error count of thedata stored in the block reaches an upper limit of a correctioncapability of the error correcting section 21. The monitoring cycle canbe set in advance to a period predicted from an error occurrence stateand various conditions, such as a range of ambient temperature, of thesemiconductor storage device 1.

As a result of the upper limit being placed on the monitoring cycle ofthe blocks with a low error count as described above, an instance can beprevented in the block registered to the first management table 31 inwhich, because the block has a low error count, the errors in the dataexceed the error correction capability of the error correcting section21 because the error count of the data is not monitored for a longperiod of time, and the correct data cannot be reconstructed.

Functions provided according to the above-described first embodiment toeighth embodiment can be arbitrarily selected and used in an arbitrarycombination.

Examples

An example of when the semiconductor storage device 1 according to eachof the above-described embodiments is a solid state driver (SSD) will bedescribed. FIG. 20 is a block diagram of a configuration of a SSD 100.

The SSD 100 includes a plurality of NAND flash memories (NAND memory)10, a dynamic random access memory (DRAM) 101, a drive controllingcircuit 102, and a power supply circuit 103. The NAND memories 10 areused to store data. The DRAM 101 is used for data transfer and as a workarea. The drive controlling circuit 102 controls the NAND memories 10and the DRAM 101. The drive controlling circuit 102 outputs a controlsignal for controlling a light-emitting diode (LED) provided outside ofthe SSD 100. The LED is used to indicate status.

The SSD 100 transmits and receives data to and from a host device, suchas a personal computer, via an advanced technology attachment (ATA)interface (I/F). The SSD 100 transmits and receives data to and from adebugging device, via an RS-232C interface (I/F).

The power supply circuit 103 receives external power supply andgenerates a plurality of internal power supplies using the externalpower supply. The internal power supplies are supplied to each sectionwithin the SSD 100. The power supply circuit 103 detects a rise or fallof the external power supply and generates a power-ON reset signal. Thepower-ON reset signal is sent to the drive controlling circuit 102.

FIG. 21 is a block diagram of a configuration of the drive controllingcircuit 102. The drive controlling circuit 102 includes a data accessbus 104, a first circuit controlling bus 105, and a second circuitcontrolling bus 106.

The first circuit controlling bus 105 is connected to a processor 107that controls the overall drive controlling circuit 102. A bootread-only memory (ROM) 108 is also connected to the first circuitcontrolling bus 105, via a ROM controller 109. The boot ROM 108 stores aboot program of each management program (firmware [FW]). A clockcontroller 110 is also connected to the first circuit controlling bus105. The clock controller 110 receives the power-ON reset signal fromthe power supply circuit 103 and supplies each section with a resetsignal and a clock signal.

The second circuit controlling bus 106 is connected to the first circuitcontrolling bus 105. A parallel IO (PIO) circuit 111 and a serial IO(SIO) circuit 112 are connected to the second circuit controlling bus106. The PIO circuit 111 supplies a status indicating signal to the LEDused to indicate the status. The SIO circuit 112 controls the RS-232Cinterface.

An ATA interface controller (ATA controller) 113, a first error checkand correct (ECC) circuit 114, an NAND controller 115, and a DRAMcontroller 119 are connected to both the data access bus 104 and thefirst circuit controlling bus 105. The ATA controller 113 transmits andreceives data to and from the host device, via the ATA interface. Astatic random access memory (SRAM) 120 is connected to the data accessbus 104, via a SRAM controller 121. The SRAM 120 is used as a data workarea

The NAND controller 115 includes an NAND interface (I/F) 118, a secondECC circuit 117, and a direct memory access (DMA) transfer controllingDMA controller 116. The NAND interface (I/F) 118 performs a process forinterfacing with the four NAND memories 10. The DMA transfer controllingDMA controller 116 performs access control between the NAND memories 10and the DRAM 101.

FIG. 22 is a block diagram of a configuration of a processor 107. Theprocessor 107 includes a data managing unit 122, an ATA commandprocessing unit 123, a security managing unit 124, a boot loader 125, aninitialization managing unit 126, and a debug supporting unit 127.

The data managing unit 122 controls data transfer between the NANDmemories 10 and the DRAM 101, and various functions related to an NANDchip, via the NAND controller 115 and the first ECC circuit 114.

The ATA command processing unit 123 performs a data transfer process incooperation with the data managing unit 122, via the ATA controller 113and the DRAM controller 119. The security managing unit 124 managesvarious pieces of security information in cooperation with the datamanaging unit 122 and the ATA command processing unit 123. The bootloader 125 loads each management program (FW) from the NAND memory 10 tothe SRAM 120 when power is turned ON.

The initialization managing unit 126 performs initialization of eachcontroller and circuit within the drive controlling circuit 102. Thedebug supporting unit 127 processes debugging data supplied from anexternal source via the RS-232C interface.

FIG. 23 is a perspective view of an example of a portable computer 2000on which the SSD 100 is mounted. The portable computer 200 includes amain body 201 and a display unit 202. The display unit 202 includes adisplay housing 203 and a display device 204 housed within the displayhousing 203.

The main body 201 includes a casing 205, a keyboard (KB) 206, and atouch pad 207 serving as a pointing device. The casing 205 housestherein a main circuit board, an optical disk drive (ODD), a card slot,the SSD 100, and the like.

The card slot is provided adjacent to a peripheral wall of the casing205. An opening 208 facing the card slot is provided on the peripheralwall. A user can insert and remove an additional device into and fromthe card slot from outside of the casing 205, through the opening 208.

The SSD 100 can be used mounted within the portable computer 22 in placeof a conventional hard disk drive (HDD). Alternatively, the SSD 100 canbe used as an additional device by being inserted into the card slotprovided in the portable computer 200.

FIG. 24 is a diagram of an example of a system configuration of theportable computer 200 on which the SSD 100 is mounted. The portablecomputer 200 includes a CPU 301, a north bridge 302, a main memory 303,a video controller 304, an audio controller 305, a south bridge 309, abasic input output system read-only memory (BIOS-ROM) 310, the SSD 100,an ODD unit 311, an embedded controller/keyboard controller integratedchip (IC) (EC/KBC) 312, a network controller 313 and the like.

The CPU 301 is a processor provided to control operation of the portablecomputer 200. The CPU 301 runs an operating system (OS) loaded onto amain memory 303 from the SSD 100. Moreover, when the ODD unit 311 canperform at least one process between reading from loaded optical discand writing to the loaded optical disc, the CPU 301 performs theprocesses. The CPU 301 also runs a system BIOS stored in the BIOS-ROM310. The system BIOS is a program for performing hardware control withinthe portable computer 200.

The north bridge 302 is a bridge device connecting a local bus of theCPU 301 and the south bridge 309. A memory controller thataccess-controls the main memory 303 is also included in the north bridge302. The north bridge 302 also provides a function for communicatingwith the video controller 304 and the audio controller 305 via anaccelerated graphics port (AGP) bus and the like.

The main memory 303 temporarily stores programs and data, and functionsas a work area. The main memory 303 is, for example, configured by aDRAM.

The video controller 304 is a video reproduction controller thatcontrols a liquid crystal display (LCD) 316 of the display unit 202 usedas a display monitor of the portable computer 200.

The audio controller 305 is an audio reproduction controller thatcontrols a speaker 306 on the portable computer 200.

The south bridge 309 controls each device on a low pin count bus 314 andeach device on a peripheral component interconnect bus 315. The southbridge 309 also controls the SSD 100 via the ATA interface. The SSD 100is a memory device storing various software and data

The portable computer 200 accesses the SSD 100 in sector units. Theportable computer 200 inputs a writing command, a read-out command, aflash command, and the like into the SSD 100, via the ATA interface.

The south bridge 309 also provides a function for access-controlling theBIOS-ROM 310 and the ODD unit 311.

The EC/KBD 312 is a single chip microcomputer in which an embeddedcontroller for power management and a keyboard controller forcontrolling the KB 206 and the touch pad 207 are integrated. The EC/KBD312 provides a function for turning ON and OFF the power supply of theportable computer 200 in response to operation of a power button by theuser. The network controller 313 is a communication device thatcommunicates with an external network, such as the Internet.

The semiconductor storage device 1 according to each of theabove-described embodiments is not limited to the SSD. For example, thesemiconductor storage device 1 can be configured as a memory card,represented by a Secure Digital (SD) card (registered trademark). Whenthe semiconductor storage device 1 is the memory card, the semiconductorstorage device 1 can be applied to various electronic devices, such as amobile phone, a personal digital assistant (PDA), a digital stillcamera, and a digital video camera, in addition to the portablecomputer.

1. A semiconductor storage device comprising: a non-volatilesemiconductor memory storing data in blocks, the block being a unit ofdata erasing; and a controlling unit monitoring an error count of datastored in a monitored block selected from the blocks and refreshing datain the monitored block in which the error count is equal to or largerthan a threshold value.
 2. The semiconductor storage device according toclaim 1, wherein the controlling unit includes: an error correcting unitcorrecting errors in data read out from the block; an error countdetecting unit detecting the error count in data corrected by the errorcorrecting unit; a monitoring unit setting the block in which the errorcount is equal to or larger than a first threshold value as themonitored block and reading out data in the monitored block at apredetermined interval; and a refreshing unit performing a refreshoperation on the monitored block in which the error count is equal to orlarger than a second threshold value larger than the first thresholdvalue.
 3. The semiconductor storage device according to claim 2, furthercomprising: a first management table to which block numberscorresponding to the monitored blocks are registered, wherein themonitoring unit monitors the error count of data in the monitored blockby detecting the error count with reference to the first managementtable.
 4. The semiconductor storage device according to claim 3, whereinthe monitoring unit deletes the block number corresponding to themonitored block on which the refresh operation is performed from thefirst management table.
 5. The semiconductor storage device according toclaim 1, wherein the controlling unit includes: an error correcting unitcorrecting errors in data read out from the block; an error countdetecting unit detecting the error count in data corrected by the errorcorrecting unit; a read-out amount detecting unit detecting an amount ofdata read out from the block; a monitoring unit setting the block inwhich the amount is equal to or larger than a third threshold value asthe monitored block and reading out data in the monitored block at apredetermined interval; and a refreshing unit performing a refreshoperation on the monitored block in which the error count is equal to orlarger than the threshold value.
 6. The semiconductor storage deviceaccording to claim 5, further comprising: a first management table towhich block numbers corresponding to the monitored blocks areregistered, wherein the monitoring unit monitors the error count of datain the monitored block by detecting the error count with reference tothe first management table.
 7. The semiconductor storage deviceaccording to claim 6, wherein the monitoring unit deletes the blocknumber corresponding to the monitored block on which the refreshoperation is performed from the first management table.
 8. Thesemiconductor storage device according to claim 6, further comprising: asecond management table to which the amount of data read out from theblock is registered, wherein the monitoring unit registers the block tothe first management table as the monitored block with reference to thesecond management table.
 9. The semiconductor storage device accordingto claim 1, wherein the controlling unit includes: an error correctingunit correcting errors in data read out from the block; an error countdetecting unit detecting the error count in data corrected by the errorcorrecting unit; a writing time detecting unit detecting an elapsed timefrom when data is written in the block; a monitoring unit setting theblock in which the elapsed time is equal to or larger than a fourththreshold value as the monitored block and reading out data in themonitored block at a predetermined interval; and a refreshing unitperforming a refresh operation on the monitored block in which the errorcount is equal to or larger than the threshold value.
 10. Thesemiconductor storage device according to claim 9, further comprising: afirst management table to which block numbers corresponding to themonitored blocks are registered, wherein the monitoring unit monitorsthe error count of data in the monitored block by detecting the errorcount with reference to the first management table.
 11. Thesemiconductor storage device according to claim 10, wherein themonitoring unit deletes the block number corresponding to the monitoredblock on which the refresh operation is performed from the firstmanagement table.
 12. The semiconductor storage device according toclaim 10, further comprising: a third management table to which writingtimes at which data are written to the blocks are registered, whereinthe monitoring unit registers the block to the first management table asthe monitored block by acquiring the elapsed time with reference to thethird management table.
 13. The semiconductor storage device accordingto claim 1, wherein the controlling unit includes: an error correctingunit correcting errors in data read out from the block; an error countdetecting unit detecting the error count in the data corrected by theerror correcting unit; a writing sequence detecting unit detecting awriting sequence in which data is written in the block in thenon-volatile semiconductor memory; a monitoring unit setting the blockin which the writing sequence number is equal to or smaller than a fifththreshold value as the monitored block and reading out data in themonitored block at a predetermined interval; and a refreshing unitperforming a refresh operation on the monitored block in which the errorcount is equal to or larger than the threshold value.
 14. Thesemiconductor storage device according to claim 13, further comprising:a first management table to which block numbers corresponding to themonitored blocks are registered, wherein the monitoring unit monitorsthe error count of data in the monitored block by detecting the errorcount with reference to the first management table.
 15. Thesemiconductor storage device according to claim 14, wherein themonitoring unit deletes the block number corresponding to the monitoredblock on which the refresh operation is performed from the firstmanagement table.
 16. The semiconductor storage device according toclaim 14, further comprising: a fourth management table to which thewriting sequence numbers are registered, wherein the monitoring unitregisters the block to the first management table as the monitored blockwith reference to the fourth management table.
 17. The semiconductorstorage device according to claim 3, further comprising: a fifthmanagement table to which registration sequence numbers of the monitoredblocks registered to the first management table are registered, whereinthe refreshing unit performs the refresh operation, when the number ofthe monitored blocks registered to the fifth management table reaches asixth threshold value, on the monitored block having a registrationsequence number decided in advance.
 18. The semiconductor storage deviceaccording to claim 17, wherein the monitored block with an earlierregistration sequence number among the monitored block is refreshedfirst.
 19. The semiconductor storage device according to claim 3,further comprising: a sixth management table to which the block numberscorresponding to the blocks in which data to be retained is not storedare registered, wherein the monitoring unit deletes the block numbercorresponding to the block registered to the sixth management table fromthe first management table.
 20. The semiconductor storage deviceaccording to claim 3, further comprising: a seventh management table towhich the block numbers corresponding to the monitored blocks registeredto the first management table and the error counts detected in datastored in the monitored blocks are registered, wherein the monitoringunit changes the predetermined intervals for the monitored blocksregistered to the first management table based on the error countsregistered in the seventh management table.
 21. The semiconductorstorage device according to claim 20, wherein the monitored blocks witha high error count, among the monitored blocks registered to the seventhmanagement table, have a shorter predetermined interval than themonitored blocks with a low error count.
 22. The semiconductor storagedevice according to claim 21, wherein the predetermined interval isshorter than a period from when errors exceeding the first thresholdvalue occurs in data stored in the monitored block until when the errorsin data stored in the monitored block reach an upper limit of errorcorrection capability of the error correcting unit.